American Heritage Dictionary
The American Heritage Dictionary version 3.5 and earlier (including version 3.0 and 3.0.1) is not compatible with Kaleidoscope. This problem was fixed in version 3.6.1 of the American Heritage Dictionary, and the latest as of this writing is version 4.0 (which also fixes this problem). Contact SoftKey for an upgrade.

SmartScroll
To use SmartScroll with Kaleidoscope, you must have SmartScroll version 2.03 or higher. You can get the latest version of SmartScroll from Marc Moini's home page: http://www.kagi.com/authors/marc/

DoubleScroll
Kaleidoscope disables DoubleScroll's live scrolling and command-clicking features. If you are not interested in these features and use DoubleScroll only for its double-headed scroll bars, then there is no problem. We are working on a fix for this problem. For now, you can try switching the load order of Kaleidoscope and DoubleScroll. However, this can confuse the scroll bar track color in some color schemes such as “Onyx”.

Retrospect, SiteMill
When the Substitute System Font feature is enabled, Retrospect and some versions of SiteMill put up a font warning box. That is because when they look for Chicago, they find Kaleidoscope's substitute font instead. This is how font substitution is supposed to behave, and there really is no problem. Retrospect and SiteMill continue to work normally once you dismiss this font warning box. Please note that this problem happens only when Retrospect is launched manually, so it does NOT prevent Retrospect from performing automated backups. There is nothing I can do about this problem, so if it annoys you, you should report this bug to the makers of Retrospect or SiteMill.

FrameMaker
When the Substitute System Font feature is enabled, FrameMaker refuses to launch, claiming it “cannot initialize the font arrays”. This problem is due to FrameMaker's over-zealous font checking, and it is not a bug in Kaleidoscope. I do not think that there is anything I can do about this, so if you want to use FrameMaker, you should just turn off font substitution.

ATM
If ATM is running, turning on Balloon Help for the Kaleidoscope control panels causes the Finder to freeze or restart. There do not appear to be any other conflicts with ATM, so you should not have a problem as long as you do not use Kaleidoscope's Balloon Help. If you simply must have the Balloon Help, change the load order so that ATM loads before Kaleidoscope. ATM 4.0 does not appear to have this problem. I am working on a fix for this.

WindowShade
Kaleidoscope is not completely compatible with the System 7.5 WindowShade control panel. If you double click the title bar of a window, the window does not collapse completely. Rather, about six pixels of the window border are left below the title bar. Please note that this is purely a cosmetic problem. If those extra pixels do not bother you, you can double click windows as much as you like. If this problem does bother you, use the WindowShade widget Kaleidoscope provides at the top right of the window title bar instead of double clicking. You will need to get used to it, anyway.

Stickies
Windows in Stickies do not have a WindowShade widget. This is because they do not need one! To collapse a Stickies window, just <option>-click on its zoom box. This is a feature of Stickies, not of Kaleidoscope.

Finder Window Background Color
When you quit from an application that modifies the system color palette, some Finder windows may be left with splotches of random colors in them. This will go away as soon as the offending windows are re-drawn. This annoyance is inherent to the system, and nothing can be done about it. This problem happens only in 256 colors.

Now Menus
If you are using Now Menus, it overrides the Kaleidoscope system font settings in some menus. If you want all your menus to use the system font you have selected in Kaleidoscope, set the font in Now Menus to “Default” and set the size in Now Menus to the same size you are using with Kaleidoscope. There really is no problem here, but some people are not aware that Now Menus provides font and size settings and may think this is a bug in Kaleidoscope.

Director, SoundEdit, FreeHand, Fontographer
The menus in these Macromedia applications are black and white instead of using Kaleidoscope's menu colors. These apps are excluded intentionally because their custom menu routines are poorly written and do not support color correctly.

Eudora
With some system fonts, the icons at the top of Eudora message windows overlap their check marks. The fonts that come with Kaleidoscope have been specially modified to avoid this sort of problem. In particular, if you want to make Espy Sans your system font, you should instead use the Espi Sans font included with Kaleidoscope.

ClarisWorks
With some system fonts, the keyboard shortcuts in ClarisWorks menus get cut off. The fonts that come with Kaleidoscope have been specially modified to avoid this sort of problem. In particular, if you want to make Espy Sans your system font, you should instead use the Espi Sans font included with Kaleidoscope.

PopUpFolder
The pop-up menus drawn by PopUpFolder do not use Kaleidoscope's menu colors. PopUpFolder's custom menu routines do not support color menus, and there is nothing I can do about this.

BeBox: Command-Clicking Finder Window Titles
Command-clicking on the title of a Finder window normally pops up a menu of all the window's parents, so you can quickly move up the folder hierarchy. Unfortunately, the Finder expects window titles to be in the middle, not at the left where BeBox puts its tab, so command-clicking on the tab does not work. There is nothing I can do about this, I'm afraid. However, you can still get the popup menu if you click in the middle where the Finder expects to find the title; BeBox gives you a six pixel thick border at the top of the window, so there is still room to click.

BeBox: Panorama, First Class, Lotus Notes
These applications all assume that the window title bar extends the full length of the window, which is no longer the case with the window tabs in the BeBox color scheme. Panorama normally gives you a popup menu if you click the window title, but it assumes that the window title is in the middle, not at the left where BeBox puts its tab. As a result, that popup menu is inaccessible. The First Class client attempts to put a progress bar in the window title bar, but with the shortened window tabs, this progress bar spills over onto the desktop (or whatever is behind the window). Lotus Notes has a similar problem.  I am working on a way to exclude these applications from the window patch when the BeBox color scheme is selected.